home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-03-06 | 1.6 KB | 50 lines | [TEXT/GEOL] |
- Item 0359931 7-July-90 15:12PDT
-
- From: MOOF Rollin, Keith A
-
- To: MACAPP.TECH$ MacApp Technical
-
- Sub: RE>>?printing C strings i
-
- Attn: Germany - Norbert Lindenberg,I
- SentBy: Keith Rollin
- Reply to: RE>>?printing C strings in
-
- Norbert,
-
- The source I was quoting was the MacApp 2.0 General Reference. The example
- even shows an application defining -103..-100 for its own use. However, for
- various reasons, I agree with the comment in the source code, rather than the
- manual (i.e, MacApp reserves the negative range, and apps get the positive
- range). The main reason is because it makes more sense to reserve just the
- negative range, rather than the positive range and just some of the negative
- range.
-
- I'm writing this on a Saturday, and don't have the luxury of calling the
- engineers and the writers to hammer this one out. However, they'll see this
- message and let me know if our determination is incorrect.
-
- - Keith
-
- --------------------------------------
- Date: 7/7/90
- To: Keith Rollin
- From: Germany - Norbert Lindenberg,I
-
- Keith,
-
- in a reply to a question about printing C strings in .Fields you write:
- "...define bCString to be a constant less than -99 (MacApp reserves
- -99..MAXINT for its own use)".
-
- {MAPInterfaces}:UMacAppUtilities.p states: "Field types for the Fields
- methods. These are understood by StdFieldToString. Negative values are
- reserved for MacApp."
-
- What’s the official policy? Did I miss some documentation that contradicts
- UMacAppUtilities?
-
- -- Norbert
-
-
-